Thanks for submitting a PR! I think this is a small improvement, it doesn't hurt, but it is symptomatic of a bigger problem. There is a whole section that describes this process: https://superset.apache.org/docs/databases/docker-add-drivers/ and I'd rather not duplicate that content. It shouldn't need to be in every single database page, ideally.

Most DB pages (for instance MySQL, Snowflake) don't repeat this info. I like how it's documented on the BigQuery page, where it links back to the main docker driver docs.

Could you instead link back to the main add driver page, copying the BigQuery example? I would merge that. Though to me it says something bigger should also be improved if we have to link back to that page from every single DB subpage.

Please include a link back to this page: https://superset.apache.org/docs/databases/docker-add-drivers/

See https://superset.apache.org/docs/databases/bigquery for example.

@sfirke, Thank you for responding.
While using Snowflake with Superset, it confused me as adding the python package in./docker/requirements-local.txt was not mentioned here.
I discovered it when I came across this ClickHouse page, and looking through this code part proved it .

I made the necessary changes as suggested by you. Currently, looking at the Snowflake page and connecting is not very intuitive. Linking back to this doc makes it easier for someone new to Superset and Snowflake.